Repository navigation
build: disable buildkit attestations on the tiered images - #13
Merged
Merged
Conversation
Buildkit attaches provenance/SBOM attestations by default, turning each
image into a multi-manifest index. Some registries -- GitLab's among
them -- reject the attestation manifest's blob on push ("blob unknown to
registry"), so a tiered image could be built but not published. These
images carry their own manifest and need no buildkit attestation, so
pass --provenance=false --sbom=false to all three builds.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Buildkit attaches provenance/SBOM attestations by default, so each tiered image (
harness/base/project) is a multi-manifest index. GitLab's container registry rejects the attestation manifest blob on push:so an image builds fine locally but can't be published. Pass
--provenance=false --sbom=falseto all threedocker buildinvocations.Note
This fixes the attestation failure. A separate, server-side limit on the reds-gitlab registry still rejects the base's multi-GB blobs (
resumable blob upload invalid) — unrelated to this change; that one needs the registry/proxy upload cap raised by an admin.